Skip to content

[rush] move sharded operation config to its own block #4923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

aramissennyeydd
Copy link
Contributor

Summary

Followup to @iclanton's comments in #4871. Moving the config for shards to its own object instead of piggybacking onto the collate operation.

As-is this is a breaking change, open to thoughts on how to roll this out safely.

How it was tested

Tested locally against the rush-redis-cobuild-plugin-integration-tests.

Impacted documentation

Schema definitions will need to be updated.

@iclanton iclanton changed the title feat: move sharded operation config to its own block [rush] move sharded operation config to its own block Sep 16, 2024
@iclanton iclanton merged commit 0f25799 into microsoft:main Sep 18, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

2 participants